chore(release): add 0.1.0 changelog and bump main to 0.2.0-SNAPSHOT#91
Merged
Merged
Conversation
Mirror the 0.1.0 changelog from `branch-0.1` (added there in apache#89) so the historical changelog stays visible on `main` going forward, and bump the parent + module versions from `0.1.0-SNAPSHOT` to `0.2.0-SNAPSHOT` to mark `main` as targeting the next development cycle. The native crate version in `native/Cargo.toml` stays at 0.1.0; that crate is published in lockstep with the Java side and will be bumped separately closer to its own release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
PR #89 lands the 0.1.0 changelog and version bump on `branch-0.1`. `main` needs two corresponding changes:
What changes are included in this PR?
The native crate version in `native/Cargo.toml` stays at 0.1.0 for now. That crate is published in lockstep with the Java side and will be bumped together when work for the 0.2.0 line actually requires a new native version.
Are these changes tested?
`./mvnw -q validate` is clean: the parent and both children resolve to the new `0.2.0-SNAPSHOT` consistently.
Are there any user-facing changes?
`main`-built artifact coordinates change from `0.1.0-SNAPSHOT` to `0.2.0-SNAPSHOT`. This is the intended effect of starting the 0.2.0 development cycle. The 0.1.0 line continues to live on `branch-0.1` (PR #89).